System and method for protection system design support

ABSTRACT

A method and system for examining, auditing, and safely evaluating process systems, including fluid pressure systems and nuclear plant systems, to aid overpressure design and/or sizing of overpressure equipment. The system includes a server subsystem, a storage subsystem, an assessment subsystem, and optionally a report generation subsystem, including computer hardware and application software for supporting these subsystems.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a Continuation-In-Part of U.S. Utility patentapplication Ser. No. 12/486,360, filed on Jun. 17, 2009, incorporated byreference in its entirety, and which claims the benefit of Ser. No.11/016,001, now U.S. Pat. No. 7,617,013, filed Dec. 17, 2004,incorporated by referenced in its entirety including the ComputerProgram Listing Appendix incorporated therein, and which claims thebenefit of provisional application Ser. No. 60/530,724, filed on Dec.18, 2003, incorporated herein by reference in its entirety, and relatedU.S. utility patent application Ser. No. 11/015,382, now U.S. Pat. No.7,565,215, filed on Dec. 17, 2004, also incorporated by reference in itsentirety.

FIELD OF THE INVENTION

This application relates generally to a method for examining and/orevaluating pressure systems.

More specifically, this application relates to a method for examiningand safely evaluating fluid pressure systems to aid overpressure designand/or sizing of overpressure equipment.

BACKGROUND OF THE INVENTION

Industry utilizing fluids under pressure, especially the hydrocarbonprocessing industry, have particularly exacting audit requirements (suchas OSHA 1910.119, for example), but the current (as of the time offiling) state-of-the-art in the hydrocarbon processing industry tendstoward manual paper analysis and archiving and/or antiquated legacydata-processing systems. This combination makes compliance activitiesvery inefficient, even when attempting to meet the minimum OSHA demands.

End users attempt to rectify this situation either by developingin-house software or by contacting outside vendors for help. This can beexpensive, and thus may not be economical solutions to the problem.

Further, for the most part, the users are not much better off using theabove approaches because such approaches lack the highly specializedengineering and software development knowledge needed to createintegrated solutions that do in fact satisfy both OSHA and end-userrequirements. Accordingly, the market needs a “Web-enabled” engineeringsoftware system that satisfies, OSHA 1910.119 audit requirements forpressure relief systems.

Thus, because the hydrocarbon processing industry has particularlyexacting Process Safety Management (PSM) audit requirements, but the“current state of the art” in today's hydrocarbon processing industrytends more to manual paper or antiquated legacy data-processing systems,an improved means for addressing the audit requirements would bebeneficial.

In an increasingly competitive environment, software technology mustsupport the ability of operating units to improve process plantproductivity (including for nuclear power plants), reduce cost and risk,and enhance manufacturing uptime. A new technology for hosting a broadrange of new forward thinking approaches and tools that can meet andsurpass these challenges is thus desired.

SUMMARY OF THE INVENTION

Provided is an evaluation system for evaluating a process system, saidprocess system comprising a plurality of equipment including aprotection device for protecting the process system. The evaluationsystem comprising: a storage subsystem for storing a computerizedequipment database including equipment information representing each ofsaid plurality of equipment; a server for serving content including someportion of said equipment information, via a public communicationnetwork, to an application executing on a remotely located usercomputer; and an assessment subsystem for automatically determining, byutilizing said equipment information, an adequacy of the protectiondevice for protecting the process system, and generating protectionassessment information therefrom.

The protection assessment information is also stored in said equipmentdatabase or in another database by said storage subsystem, and thecontent served by the server includes some portion of said protectionassessment information.

Also provided is a method for evaluating a process system. comprising aplurality of equipment including a protection device for protecting theprocess system.

The method comprising the steps of: storing equipment informationrepresenting each of said plurality of equipment in a computer database;serving content to an application executing on a user computer;automatically determining an adequacy of the protection device forprotecting the process system using the stored equipment information;automatically generating protection assessment information using resultsfrom the assessment process; and storing some portion of said protectionassessment information in said computer database or in another computerdatabase.

The content includes some portion of said protection device informationand some portion of said protection assessment information.

Still further provided is a method of performing a PSM assessment of aprocess system by using the assessment system and/or assessment methoddescribed above.

Also provided is a method of performing a PSM assessment of a processsystem using the above system and/or method.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other features and advantages of the present inventionwill become apparent to those skilled in the art to which the presentinvention relates upon reading the following description with referenceto the accompanying drawings, in which:

FIG. 1 shows a block diagram representing the Evaluation System;

FIG. 2 is a schematic showing a simple embodiment of the EvaluationSystem;

FIG. 3 is another schematic showing a more complex embodiment of theEvaluation System;

FIG. 4 is a diagram representing a possible implementation and use ofthe Evaluation System in a commercial embodiment, iPRSM™;

FIG. 5 is a structure map showing a structure of a commercial embodimentof the Evaluation System, iPRSM™;

FIG. 6 a is a work flow diagram for a Relief Valve project as acommercially available embodiment of the iPRSM™ system might be used;

FIG. 6 b is a Flow Chart showing an implementation of a commerciallyavailable embodiment, iPRSM™, might be utilized for performing anevaluation;

FIG. 7 is a screen shot of a commercially available embodiment, iPRSM™,showing a schematic of a process system being evaluated;

FIG. 8 provides an overview of an example embodiment of the EvaluationSystem using the iPRSM structure;

FIG. 9 provides a project workflow diagram of the example embodiment ofFIG. 8; and

FIG. 10 provides an architecture model of the example embodiment of FIG.8.

DETAILED DESCRIPTION OF THE EXAMPLE EMBODIMENTS

Process Safety Management (PSM) is critical to process plant design andoperation. Process safety management includes all aspects of plantsafety control. Pressure Relief Systems Management (PRSM) is a keycomponent of process safety management. The management and auditing ofpressure relief systems compliance is necessary for the fulfillment ofOSHA PSM compliance requirements and industry insurance requirements.Note that throughout this document, the invention is described as theEvaluation System (or System or iPRSM™), whereas the system to beevaluated by the Evaluation System is known as the process system or theprocess system to be evaluated.

The invention is a method and/or system, including a computer programfor running on a computer (hereinafter the “Evaluation System” or the“System”). The Evaluation System is a PRSM software application that canbe utilized to help ensure that process plants operate under theprotection of safe pressure relief systems at all times. The EvaluationSystem is used to evaluate and assess the safety and operation of aprocess system design (e.g., a process plant or subsystem thereof). In aproposed commercially available embodiment, shown in FIG. 4, theEvaluation System is to be called iPRSM™. FIG. 4 shows a top-level viewof a preferred embodiment of the system in the context of its commercialuse.

The Evaluation System, especially with its Web-centric technology in apreferred embodiment, allows plant personnel, auditors and engineeringpersonnel instantaneous/concurrent access and analysis to data on anypressure relief system, from any location that has web connectivity.These personnel can quickly resolve problems from this ability, whileoffering the most thorough and systematic approach for the design,analysis, and documentation of new or existing pressure relief systems.From compliance to third party audits, this preferred solution offers anall-inclusive workflow and information management infrastructure thatallows operating facilities to develop and maintain comprehensive modelsof their pressure relief and vapor disposal systems.

The Evaluation System addresses the proactive management of reliefsystems safety compliance according to best-practices principles,including the management of compliance-related as-operating data theongoing verification of standards-based compliance and produces tasksfor plant management reports for regulatory purposes. The net result canbe safer plants and major cost savings due to the elimination ofduplication of effort in plant data recording and tracking.

In its preferred embodiment, the System as implemented:

-   -   Fulfills all OSHA CFR 29 1910.119 documentation requirements;    -   Provides instantaneous access to real time and reliable data;    -   Evaluates any pressure relief device—valves, rupture disks,        conversation vents, vacuum breakers, emergency vents, etc.;    -   Includes all hydraulic piping calculations;    -   Includes engineering and catalog data for all major PRV        manufacturers;    -   Is integrated to a comprehensive thermo-physical property        package;    -   Import/Export capabilities to any platform    -   Assists the practical needs of plant operators and application        engineers; and    -   Provides a reduction in cost/time/risk for management pressure        relief design systems.

In its preferred embodiment, the Evaluation System allows centralizedinstant access, analysis and management to live data, at multiplelocations, from anywhere in the world. It uses the web standard securetransport protocols (SSL encryptions & HTTPs) as all major financialinstitutions and secure e-commerce sites. Combined with complete useraccess controls, the System assures proper transaction management forconcurrent users.

The System is Platform/Hardware Independent, and utilizes an Openarchitecture framework which allows the System to run on virtually anyplatform—Linux®, Unix®, Windows® or Macintosh®, for example.

The System can be implemented in a Standalone mode, on a LAN (e.g., anintranet), or on a WAN (e.g., the Internet). It can utilize anycompliant browser, and can be implemented on any server platform (e.g.,Windows, Linux, and Unix).

The system can utilize any commercially available database applicationor standard, and any hardware that is Windows based, Linux based, orMacintosh based. Furthermore the system will preferably utilize aMulti-user Architecture.

Pressure Relief Safety Management (PRSM) is a collaborative effort whichsupports concurrent access and Multi-tasking functions. It providesAccess Control—who gets to do or see what.

The System is intended to be a tool for support of “Management ofChange”. Management of Change (MOC) is an activity to documentmodifications to a process, such as changes in plant equipment and/ordesign, for example. In most cases, it also refers to the actualdocument that is used to initiate a change. The Evaluation Systempreferred solution has an explicit workflow model that automaticallyprovides an ideal “management of change” protocol. The System's MOC isused to initiate all modifications and becomes part of a documentedworkflow process, which defines the reason for the change, approvals andreviews, schedule or priority, and completion verification. Thisincludes a comprehensive “signoff model” where all changes are digitallysigned and recorded. It includes a stand-alone repository for equipmentrecords, queue for management of changes and PHA follow-ups.

The System provides Data Import/Export Capability, which can link to anyrelational database by plug and play; spreadsheet templates can also beused to import/export data. It is designed to support collaborativework.

Furthermore, the preferred System supports remote auditing of plants byOSHA inspectors. The multi-user interface and web-based system allowsmultiple users to access information using full or read only accesslevels. This allows remote audit capability by inspectors or review andcollaboration by colleagues.

The System also provides a “Centralized Document Repository” that can bestored in electronic format. In order to properly manage a plant'spressure relief system, engineers need to have access to a wide varietyof information about all aspects of the plant itself. As complete a“paper trail” as possible should to be captured in digital format andstored as a component of the pressure relief systems management process.This information can then be provided to system users in both graphicaland textual form.

Information tracking and archiving requirements are typically the samefor both new and existing installations. The preferred System cansupport starting with a new installation and keeping complete recordsfrom the beginning than to track down or reconstruct this informationafter the fact. The System document repository will also allow the userto digitize legacy paper data and store the digitized data itscorresponding equipment.

To properly manage a plant's Pressure Relief Systems and to ensure thevalidity of the audit process, the preferred System can capture, trackand document all changes that are made to the plant.

The System preferably will capture and record, for example:

-   -   design data;    -   as-built data;    -   equipment data;    -   maintenance data;    -   inspection data; and    -   historic data.

The preferred System is designed to provide needed “Industry Documents”as required by ASME, API, OSHA, EPA, etc. “Site Reference Documents”,including Physical Properties Database, Relief Safety Manuals, etc. willalso be supported. Software Documents, such as an interactive usermanual, for example, are also provided to aid the user of the preferredSystem.

The preferred System will also provide “Groupware Tools”, which areimportant for administration and project management. Meetings,deadlines, and milestones which need to be available to broadercommunity are supported.

Further supported by the preferred System are Internal Email Functionsfor keeping email and notes are part of groupware, useful to keep ahistorical perspective.

An “Internal Task Queue Manager” can also be provided with a singleinterface to manage all work on all tasks with other users from withinthe same program.

An Integration to “Flash Calculation Engine” and “Thermo PhysicalProperties System” is preferably provided. The preferred System hasintegrated the VMGThermo thermo physical property system from VirtualMaterials Group, Inc., providing a leading position in thermo physicalproperties. Although the assumption of steady-state conditions provesadequate for most pressure relief system evaluations, the comprehensiveflash calculation engine and mixture physical properties also allowaccurate and creative solutions involving thermodynamics. The preferredSystem can also be integrated with any physical properties database viaa spreadsheet interface approach.

The System also provides an “Architectural Model” which preferablyensures that all the pieces of equipment in all the protected systemsare appropriate for their application, in light of all the failurescenarios including overpressure contingency scenarios that have beenattributed for each of the protected systems in a plant.

Furthermore, the System user interface uses a hierarchy approach withthese main components: “Plants”, “Units”, “Protected Systems”,“Equipment”, and “Overpressure Contingency Scenarios”.

Plants are comprised of units and equipment assigned to units. Equipmentprovides protection, requires protection, both, or neither; andEquipment has fittings: inlet/outlet. Units are comprised of protectedsystems. Protected Systems are comprised of linked pieces of equipment,with system sketches portraying the protected systems. And OverpressureContingencies are assigned to protected systems, and describe potentialscenarios of concern to be evaluated by the System. CalculationParameters are linked to specific equipment attributes, and “AssociatedDocuments” are linked to equipment.

The System provides a “Protected System Model” which preferably ensuresthat all the pieces of equipment in all the protected systems areappropriate for their application. All the overpressure contingencyscenarios that have been attributed for each of the protected systems ina plant are calculated and documented.

The preferred System also supports an “Equipment Abstraction Model” forsupporting an arbitrary number of equipment types. The basic idea isthat any kind of equipment can be linked to a protected system in one offour roles: protected, protecting, overpressure source, or ancillary.

A “Causes of Overpressure Abstraction Model” is also provided in thepreferred embodiment, which includes all API “causes of overpressurescenarios” included as failure scenarios. The scenarios are deemedapplicable or not, and will indicate which ones have been considered inthe final relief study. There are many events which may cause theinternal pressures to rise above mechanical design limits of aprocessing unit. The one common aspect of relief occurrences is thatsomething has caused the balance of mass and energy entering and leavinga system to be disturbed to the point where the imbalance cannot beabsorbed without the pressure rising above mechanical limits.

The preferred System will also support a “Maintenance Database” havingmaintenance records linked directly to equipment records.

The preferred System will further support an “Automated Workflow Model”,which is an explicit workflow model which automatically manages thesteps the user needs to follow to get the job done. This includeskeeping track of who and when took each step (by person login id, forexample).

The preferred System also support navigation through P&ID's or SystemSketches, whereby a user can navigate to any piece of equipment (whichhas all associated calculations & documentation) by simply calling up aP&ID image and make a selection with the click of a mouse. Unit drawingsand system sketches are directly linked to pieces of equipment.

A “Signoff Model” is a workflow model which includes signoff steps ateach and records changes and signoffs as they are made. A “PermissionsModel” protects data access and workflow steps and can be controlled byper-user access levels. “Revision Control” provides a History that isautomatically managed and archived, with all changes electronicallysigned to record the user revisions. Closing the revision prohibitingany changes until a new revision is opened locks versions of protectedsystem evaluations. Revision Control is controlled by access restrictionto super users.

“Worksheets and Units” maintains computational integrity of thestandards-base calculations and units. “Dependency Links” are used tolink pieces of information not covered in the standards and workflowthat influence decisions but that are not explicitly identified, andprovide links to associated documents.

The preferred System supports various “Engineering Functions” as well.“Sizing for Pressure Relief Valves” includes sizing for conventional,bellows, and pilot operated relief valves, and includes ASME Sec I, III,VIII, and Non-Code, and supports Vapors, Gases, Steam, Liquid, 2phase

The preferred System supports “On-Line Relief Valve Selection” whichprovides an on-line automated relief valve model configurator. Thison-line configurator will simplify the selection process by selectingthe optimum PRV for most ASME code or non-code applications. Thepreferred System will deliver the basic valve series, orifice,construction, materials (based on temperature and pressure), andinlet/outlet valve configuration. All selections have been generated toensure all ASME, API and generally good engineering practices have beenadhered to.

The preferred System also supports “Sizing for Rupture Disks” whichincludes all rupture disk devices, and includes rupture disk andholders. “On-Line Rupture Disk Selection” provides an on-line automatedrupture model configurator. This on-line configurator will simplify theselection process by selecting the optimum PRV for most ASME code ornon-code applications. The System will preferably deliver the basic disktype, size, material, disk holder, and maximum ratings. All selectionshave been generated to ensure all ASME, API and generally goodengineering practices have been adhered to.

The preferred System also supports “Sizing for Atmospheric ConservationVents”, which includes pressure and vacuum vents, and pallet-weight andpilot operated vent breathers. “On-Line Conservation Vent Selection” isalso supported, which provides an on-line automated conservation ventmodel configurator. This on-line configurator will simplify theselection process by selecting the optimum PRV for most ASME code ornon-code applications. The System will deliver the basic valve series,orifice, construction, materials (based on temperature and pressure),and inlet/outlet valve configuration. All selections have been generatedto ensure all ASME, API and generally good engineering practices havebeen adhered to.

The preferred System supports “Determination of Relief Requirements”,which are conditions for which overpressure protection may be requiredfor pressure vessels and low pressure storage tanks. The System alsosupports “Relief Load Calculations” which are systematic identificationof all potential overpressure scenarios and relief load calculations aredetermined and associated with each piece of equipment. Specificequipment operating and design attributes or parameters are linkeddirectly to relief scenario calculations ensuring ease of identificationof impacts of operation, design, or hardware changes to ensurecontinuous overpressure protection adequacy.

Further supported are “Fire Vapor Generation” providing relief capacitydue to effect of fire of the wetted surface of a liquid filled vessel;“Fire Gas Expansion”, providing relief capacity due to effect of fire ofthe wetted surface of a gas filled vessel; and “Tube Rupture” (HeatExchanger) providing capacity determination of a high pressure (tuberupture) stream over pressuring equipment on the low-pressure side of aheat exchanger; “Control Valve” providing capacity determination of anautomatic control valve failure; “Pump Head Calculations” for determinepump head (capacity) calculation; and “Thermal Expansion” providingliquid/thermal expansion calculations

Preferably, Inlet/Outlet Pipe Loss calculations are supported byproviding a comprehensive library of inlet and outlet pipe fittings andcontains parameters that identify the size and equivalent lengths or Kcoefficients. These are then used for computing the pressure profile foreach section of piping. Force and moment calculations, AcousticalInduction Vibration calculations, and Noise level calculations are allsupported. “All Overpressure Scenario Area Calculations” providerequired area calculations (per individual OVP scenario) based onASME/API requirements.

“API Omega Appendix D -2Phase Flow” provides two-phase reliefcalculations are based upon the Design Institute of Emergency ReliefSystems (DIERS) methodologies. The API Omega model has been standardizedin the System.

“Multiple Pressure Relief Valve Applications” which are someapplications in which more that one relief valve is required to satisfythe required area, is preferably supported. “Layers of ProtectionAnalysis” (LOPA) simplified risk assessment methods are also preferablysupported.

Equipment Libraries: The System preferably supports an arbitrary numberof equipment (or device) types. These individual pieces of equipment canbe classified as” providing protection, requiring protection, orneither. All pieces of equipment can be assigned descriptive data thatphysically describes model, configuration, and identification. Equipmentthat is classified as “protected” or “protecting” also has definedvariables that provide process data.

Supported equipment Includes: Block Valves; Control Valves; Compressors;Heat Exchangers; Relief Valves; Pumps; Rupture Disks; Tank Vents; SteamTurbines; and Vessels, for example.

“Relief Valve—NB Redbook” which contains information of National Boardpressure relief certification data, is supported by the System, whichcontains a information of National Board pressure relief certificationdata including manufactures such as Farris, Consolidated, Crosby andAnderson Greenwood.

A “Pipe Fitting Catalog”, which contains comprehensive library of inletand outlet pipe fittings and standard pipe schedules, can also besupported. The forces imposed by external piping often affect pressurerelief devices. These forces may be due to dead loads of pipingcomponents, loads induced by thermal expansion, and loads induced bymomentum forces of fluid flow. The System has a comprehensive library ofinlet and outlet pipe fittings and contains parameters that identify thesize and equivalent lengths or K coefficients. These are then used forcomputing the pressure profile for each section of piping.

The preferred System provides a number of “Deliverables” that meet OSHA29 CFR 1910.119 documentation guidelines. Equipment databases includingall relevant parameters are created. The “Repository includes alldigital documents, including: P&ID documentation; ISO piping drawings;CAD drawings of all relief devices inlet/outlet piping; CAD drawings ofall flare header systems; and Original equipment datasheets,calculations, certifications.

Additional deliverables/results preferably include: Identification ofall relief contingencies for all devices; quantification of requiredrelief rates; orifice area calculations for all relief devices;inlet/outlet piping loss calculations for all devices; mechanicalevaluation of applicable devices (noise level, reaction forces,acoustical vibration analysis); complete documentation package includingall calculations, drawings, spec sheets, etc.; automatic updating offiles according to changes in codes; accessibility and standardizationof enterprise wide users; and a wide variety of HTML reports, all foraiding in the assessment of the process system being evaluated, and toaid auditing and review processes.

Evaluation System Architecture:

FIG. 1 is a block diagram showing a simplified view of the EvaluationSystem 1 in the context of its use environment. In an abstract,generalized description, the System 1 is comprised of a server subsystem2, which can be implemented, for example, by including a server 3 and areception subsystem 4, although the server 3 and reception subsystem 4may be combined into a single server application (running on a singlecomputer, for example), as another example.

The Evaluation System 1 also comprises a storage subsystem 5 for storingdata and equipment information described in more detail, both above andbelow. The storage subsystem can utilize any of a number of computerdatabase applications (e.g., SQL, objected oriented databases, etc.) andstorage devices (e.g., RAM, ROM, hard drives, CD ROMs, DVD, etc.)

The equipment information includes diverse information about variousprocess equipment of the process system being assessed. Equipmentdrawings, maintenance information, manuals, relationships to otherequipment, location, etc., examples of which are discussed throughoutthis disclosure, can all be included in the database(s).

The Evaluation System further comprises an assessment subsystem 6 forperforming evaluations of the process system being examined. Theassessment subsystem has the computer application code and hardwarenecessary to evaluate the process system being examined using theequipment information in light of various failure scenarios (many ofwhich may be known for any given type of equipment).

The assessment subsystem will utilize some portion of the equipmentdatabase to perform the evaluation/assessment. Obviously, someinformation relating to the protection equipment being evaluated must beutilized. Furthermore, information about the equipment or subsystemsbeing protected by the protection equipment being evaluated will alsolikely be utilized in the assessment. However, there may be portions ofthe process system being evaluated that are not relevant to theparticular scenario or equipment being assessed (e.g., too remote,isolated, or no impact), and data related to that irrelevant portion maybe ignored.

The Evaluation System 1 may further comprise a report generatingsubsystem 7 for generating reports useful in evaluating the processsystem, for performing audits, and for capturing the assessment results.

The Evaluation System 1 interacts with one or more users 10 via theserver subsystem 2, which can include a server 3 and a receptionsubsystem 4. Via the server subsystem 2, the users 10 can receive dataand information from the System 1 through the server 3, and provide dataand information to the System 1 through the reception subsystem 4.

For example, the sever subsystem 2 may be implemented using acommercially available web server, which can be used to both send (i.e.,serve) and receive information from a user. Thus, a single commercialapplication could be used to implement the server subsystem 2. However,for more complex operations, the various subsystems could be distributedacross a number of computers, each running one or more applications tosupport the allocated subsystem.

Similarly, the report generation subsystem 7 and/or the assessmentsubsystem 6 could be distributed across multiple computers, implementedon the same computer, or combined with the storage subsystem 5 andserver subsystem 2 on a single computer. The software of the ComputerProgram Listing Appendix in the related application contains examples ofcode for implementing the System, including the report generationsubsystem 7 and the assessment subsystem 6.

The storage subsystem 5 can utilize a custom or commercially availabledatabase application running on one or more dedicated, or shared,computers. The data can be stored on any of a number of storage device,including disc arrays, disc drives, RAM, ROM, CD ROMs, DVD ROMs, tape,or any other medium appropriate for electronic data storage.

FIG. 2 shows an example implementation 1A of the Evaluation System 1, inone of its simplest forms. The system 1A comprises a server 12, adatabase 14, and a router/modem 16 to connect to a public communicationsnetwork 20. A user 10A, utilizing a workstation 18, is also connected tothe communications network via a router/modem 19, for example. In thisimplementation, the server 12, along with the database 14 androuter/modem 16 and the appropriate software, implement all of thesubsystem functions of the System 1 by running various applicationprograms on the server 12 hardware, for example. Of course, the system1A may also support additional users in a manner similar to that shownfor user 10A, for example.

The preferred embodiment can utilize the Internet as the publiccommunications network. However, other communications networks could beutilized, such as telephone networks, cellular networks, dedicatednetworks, cable TV networks, power lines, etc. Because of the ubiquitousnature of the Internet, a solution utilizing that diverse network (whichcan utilize many individual communications networks) is most appropriateat this time.

FIG. 3 shows a more complex implementation 1B of the system 1. In thissystem 1B, a plurality of servers 21A-21 n can be utilized to implementthe server subsystem 2 functions of FIG. 1. Further, a plurality of CPUs23A-23 n can be utilized to implement the assessment subsystem 6functions of FIG. 1. A plurality of database storage devices 25A-25 ncan be used to implement the storage subsystem 5 functions of FIG. 1.And a CPU 30 and printer 31 can be used to implement the reportgeneration subsystem 7 functions of FIG. 1, for example. Finally, arouter 29 can be used to connect to a Public Communications Network 35(such as the Internet, for example).

Note that, although FIG. 3 shows multiple servers 21, CPUs 23, anddatabases 25, any of these might be implemented on one or more computersin various configurations, as desired. As the number of users supportedby the system 1C grows, additional hardware can be added to increase thecapacity of the system.

Continuing to use FIG. 3 showing the more complex implementation 1B, aplurality of users can be supported in various configurations. Forexample, a plurality of users 10B operating single workstations 18A-18n, individually connected to the public communications network 35, canbe supported. Furthermore, complex user networks can also be supported,as represented by the example shown in 10C. Of course, the EvaluationSystem of FIG. 1 might also be utilized to support users in the mannerof 10B and 10C, as well.

FIG. 5 shows a structure map of the software design of a commerciallycontemplated version of the Evaluation System known as iPRSM™. Thisstructure map represents the software contained in the Computer ProgramListing Appendix in the related application, incorporated herein byreference.

For supporting multiple users, the Evaluation System will serve andreceive information related to those users according to the interestand/or access rights of the individual user. Thus, different users maywish to view and/or evaluate different parts of the process system beingevaluated. However, as equipment information is updated, any userwishing to view that information will then receive the updatedinformation. Furthermore, assessment results and/or reports generated byone user may be viewable by another user. The different users may wellbe remotely located from each other.

It is clear that the implementations shown in FIGS. 2 and 3 are merelyrepresentative of two example system designs. There are numerous otherpossible hardware implementations of the system functionality that fallwithin the scope of the invention and the claims.

The Evaluation System is preferably implemented as a web-basedapplication available over the Internet, using various scripting ordedicated applications to provide added benefit (including assessmentcapability, for example). The Evaluation System can preferably utilize acommercially available web browser to connect to a database over a LANor Internet connection. In many ways it acts like most web sites, withweb pages that can be opened with hyperlinks (“links”) to additional webpages.

The pages that are viewed are composed of data that resides in one ormore database storage devices, and is prepared for the user each timethe user visits a page. There are special links that perform variousoperations with that data, which may display a new page, or refresh theview of a current page.

The Evaluation System served data can preferably be used by any industrystandards-compliant browser in default configuration having JavaScript,cookies, and popup windows enabled.

The Evaluation System preferably uses JavaScript for its controls, andthe Evaluation System uses a temporary cookie to manage userinteractions throughout the application. This cookie is not retainedwhen the user closes a browser. The Evaluation System also uses pop-upwindows for its transactions with the database, and for various smallpages. Any “ad-blocking” software that traps pop-up windows should bedisabled for proper operation.

A LAN/Internet connection, preferably a broadband-quality connection, isrecommended. Third-party plug-ins may be utilized along with the webbrowser. Examples of such plug-ins are Microsoft Word, Excel, and AdobeAcrobat.

The Evaluation System in a preferred embodiment can be used to managesensitive data that should adhere to strict standards for correctnessand completeness. It is designed to safely and securely use a publicmedium: web pages over the Internet or over a LAN. To deliver a secureddatabase system over a public medium the Evaluation System utilizes bestpractices security features, including Login access, requiring a LoginId and Password distributed by a system Administrator. Without a validID and password, visitors to the Evaluation System will be able to viewonly the Login page and several purely informational pages.

FIGS. 6 a and 6 b are representations of the use of the EvaluationSystem to evaluate a process system. FIG. 6 a shows a workflow for suchan evaluation process. FIG. 6 b is a flow chart describing theevaluation process in more detail. Note that at some point, all of thenecessary equipment information describing the process system must beproperly entered into the Evaluation System database. Equipment listsand tool sets provided by the System support this task, althoughcustomized equipment can also be entered.

FIG. 7 shows a screen shot of a schematic diagram of part of an exampleprocess system to be evaluated by the Evaluation System.

The Evaluation System includes an equipment database and a scenariosdatabase, allowing an engineer to input process specific information toproperly determine suitable overpressure relief for that process. Theengineer has the option to design or evaluate a single relief (failure)scenario or multiple relief scenarios based on the specifics of thatparticular process. From a design standpoint, the engineer must inputequipment information and scenario information pertaining to the piecesof equipment in the process, the process conditions, the type and numberof relief devices desired, the potential causes of overpressure, and thematerials involved in the process. Once entered, the data enables theSystem to determine the proper communication between data within thedatabase to perform the appropriate calculations to determine the sizeof the relief system (and/or devices) needed to protect againstoverpressure from the potential causes thereof.

From an evaluation, or auditing standpoint, the Evaluation Systemsupports evaluating current pressure relief systems to ensure thatchanges, made or proposed, to the process have not exceeded the currentrelief capacity of the pressure relief system. In this manner, theengineer proceeds by selecting the portion of the relief system beingevaluated by entering identifying numbers of the proper relief devices,and entering information pertaining to the equipment in the process, theprocess conditions, the potential causes of overpressure, and thematerials involved in the process. The Evaluation System again uses thisinformation to select the appropriate equations and determine a reliefcapacity and an area required for said capacity from the selectedequations. These values can then be compared by the engineer to theequivalent values of the devices currently in place.

Lists of equipment, including relief devices, and causes ofoverpressure, are all input into the Evaluation System (or provided aspart of an Evaluation System tool set). Pressure relief valves andrupture disks, for example, those manufactured by Curtiss-Wright FlowControl Corporation (“Curtiss-Wright”) or its predecessors, are includedin a relief devices list, and each relief device in that list is linkedwith information pertaining to the physical properties of the reliefdevice. Furthermore, devices produced by manufacturers other thanCurtiss-Wright can also be engineered and evaluated using the EvaluationSystem by inputting a manufacturer specific identification code for theappropriate pressure relief device in the relief devices list, andentering the appropriate parameters and descriptions, if necessary.

The causes of overpressure list in the Evaluation System includes causesof overpressure that are known to commonly occur in a processingfacility, and aid in determining the failure scenarios and theirresults. Engineers using the Evaluation System are presented with theoption of selecting from an Evaluation System database the causes thatmay potentially occur in a particular process. Once the causes ofoverpressure are selected, the Evaluation System can initiatecommunication between the causes of overpressure list and the equipmentlist to calculate the expected relief load capacity. From this expectedrelief load capacity, the Evaluation System can properly determine thesize of the overpressure relief devices necessary to safely protectagainst equipment failure due to over pressurization.

The relief devices for a plant must be installed in a process withsufficient inlet and outlet piping capacity to safely accommodate thesimultaneous overpressure of a plurality of pieces of equipment. Anengineer can use the Evaluation System to determine the inlet and outletpiping necessary for the relief scenario selected. Accordingly, theEvaluation System provides the tools to allow an engineer to quickly andsafely design or evaluate the relief capabilities associated withproduction processes.

Furthermore, the Evaluation System preferably utilizes anobject-oriented database structure.

The goal of Pressure Relief Systems Management is to ensure that plantsare operating under the protection of safe pressure relief systems atall times. The key to achieving this goal is the proactive management ofrelief systems safety compliance according to best-practices principles,including the management of compliance-related as-operating data and theongoing verification of standards-based compliance.

A successful PRSM process according to the invention produces tasks forplant management, reports for regulatory purposes, and safer plants. Toensure that a plant remains compliant over time, the Evaluation Systemcan aid in:

-   -   conducting periodic relief systems audits;    -   submitting audit reports at appropriate intervals;    -   correcting instances of non-compliance identified by audits; and    -   performing “what-if” evaluations that compare the current audit        with hypothetical audits performed using newer or older versions        of the calculation worksheets.

Those who participate in proactive PRSM processes using the System canfaithfully implement the engineering standards that the engineerutilizes on for the determination of compliance. The System shouldsupport the participants collaborative opportunities and respect theirworkflow management needs. It must also implement best practices fromsoftware engineering, especially in the areas of security and multi-userdatabase access protocols. The Evaluation System can provide thissupport for PRSM. The preferable aspects of the Evaluation System are:

Standards Compliance: the Evaluation System preferably uses ASME and APIstandards-based evaluation of possible overpressure contingencies.Hazard analysis is equipment-based, rather than relief-device-based, toensure that all equipment is properly protected.

Calculation Worksheets: the Evaluation System can contain a complete setof ASME/API standards-based engineering worksheets for accurateconsistent calculation of relief flow rates, orifice areas, inlet/outletpiping losses. Installations that are inconsistent with industrystandards and codes can be flagged and identified. Calculationworksheets are under version control, and every evaluation is recordedwith respect to the version of the worksheet used to perform theevaluation.

Traceability: the Evaluation System aids the user to establishingdependency links between the parameters used to perform a hazardanalysis on a piece of equipment and other worksheets and equipmentcharacteristics that were used to determine those parameters. This meansthat decisions can then be traced back to their assumptions. If anassumption changes, then analyses based on these assumptions are flaggedby the Evaluation System as needing to be re-examined for protectionimplications. Other system features include:

Import/Export Data can be imported/exported between the EvaluationSystem and other tools, such as flare header design tools, or inspectionand maintenance data systems.

Standards Tracking: the Evaluation System maintains historical versionsof standards calculation worksheets. When a standard changes, the impactof the proposed changes can be evaluated relative to the current hazardanalysis.

Evergreen Data Management: the Evaluation System enables consolidatedevergreen data management to maintain a current picture of operations inorder to minimize hazards and re-evaluation errors and costs.

Workflow Support can be provided for:

-   -   Allowing selection of reasonable tasks;    -   Preventing selection of unreasonable tasks; and    -   Recording signoffs for appropriate tasks.

History Tracking and Archiving can be provided for:

-   -   Recording changes and signoffs as they are made;    -   Users can make queries such as who changed and who approved        what, when, and why;    -   Reporting for summarizing changes over specified time periods;        and    -   Maintaining Prior versions of data for review and change        comparison.

Evaluation System Collaboration can be:

-   -   designed to support collaborative work;    -   support concurrent access by multiple users over a network;    -   support multi-tasking of a user's activities;    -   provide generic groupware tools such as task queues, discussion        groups, and mailing lists; and    -   can interface to other software tools.

As discussed in detail above, the Evaluation System is designed formulti-user web-based access using standard commodity browsers. Thismeans that the Evaluation System can be used from any workstation with astandard browser without requiring the installation of any additionalclient software. The Evaluation System including its associated databasecan reside on a distinct server.

Control of access to pages, workflow, and database records can becontrolled according to the privileges of the logged-in user. Becausethe preferred http protocol is connectionless, the Evaluation System canprovide full support for server-side session and page instance data,with a secure login and session management scheme. To support multipleconcurrent transactions, the Evaluation System can also provideautomatic enforcement of end-to-end optimistic locking. This can be usedto prevent concurrent users from taking action based on obsolete data,such as generating a report while other engineers are altering equipmentdata.

Because the Evaluation System's web applications are preferablytransaction based, they can be made to fail safely. The EvaluationSystem can use a structured exception handling mechanism which ensuresthat if anything goes wrong during the processing of a transaction: (1)no changes are made to the database, and (2) the user is informed of thefailure, and the failure is logged (along with relevant debugginginformation). From the perspective of the Evaluation System, it isbetter to fail correctly than to proceed wrongly. The Evaluation Systemcan help minimizes technology risks by not relying on uncommontechnology or technology that can be changed on a vendor's whim.

The Evaluation System can be used to help minimize the above identifiedrisks as follows:

-   -   Evaluation System programs can be made to work with any        standards-compliant web browser, such as Netscape Navigator, and        Microsoft Internet Explorer, for example. Internet Explorer        issued as the Evaluation System's principal test browser.    -   Evaluation System programs can be made to work with any        CGI-compliant web server, in particular Microsoft IIS and        Apache, for example. Apache is available on all Microsoft and        Unix-like back ends and is one of the top web servers in use.    -   The Evaluation System includes its own database management        system (DBMS), with full support for atomic transactions and        referential integrity. Testing has shown that the Evaluation        System DBMS is faster than an outboard DBMS for databases of the        size required by a typical application. Alternatively, the        Evaluation System can utilize any of the common DBMSs for its        back-end database functions, including Postgres, Oracle, and        DB2, as required, for example.    -   The Evaluation System also preferably has a real-time        distributed transaction logging facility, which allows multiple        (geographically dispersed) machines to keep hot-backup copies of        the production database. In the event that the primary service        disappears, the site administrator can simply point the domain        name service to the next-level backup machine, and the        Evaluation System will pick up from the point of the last        successfully completed transaction.

The system was designed from the ground up with a best-practicesevolvable architectural structure, and to provide an optimal set ofdeployment options to the application customer according to their budgetand infrastructure needs. The following models are preferablyimplemented:

Plants & Units model: Equipment and protected systems are organized intoa plants and units hierarchy. When there is a large amount of equipmentinvolved, some sort of organization for access is beneficial.

Protected system model: The basic concept is that any kind of equipmentcan be linked to a protected system in one of four roles:

-   -   protected,    -   protecting,    -   overpressure source, or    -   ancillary

The protected systems also have per-system data.

Multiple Valves model: The protected system model preferably explicitlyhandles multiple valves.

Equipment abstraction model: the Evaluation System can support anarbitrary number of equipment types, including Protecting Equipment andProtected Equipment, for example.

Cause of Overpressure abstraction model: the Evaluation System cansupport an arbitrary number of overpressure types, each of which has itsown flowchart.

Document database: A document database is preferably provided, whereindocuments can link to plants, units, equipment, systems, and causes ofoverpressure.

Maintenance database: A maintenance database that links to equipment ispreferably provided.

Workflow model: An explicit workflow model is preferably implementedthat automatically manages the steps the user needs to follow to get thejob done. This includes keeping track of who took each step (by personlogin id) and when.

Signoff model: The workflow model preferably includes signoff steps, andcan keep track of who did each signoff and when.

Version Control model: A revisions database is preferably provided,linked to protected systems, for tracking versions of equipment,protected system, and causes of overpressure signoff.

Permissions model: Data access and workflow steps can be controlled byper-user access levels.

Worksheets and Units: Units handling is preferably provided. Engineeringvalues know their units category and style, so any variable in validstyle (such as inches, feet, or meters, and pounds or kilograms), can belooked, at but the underlying calculations are preferably always done inwhat engineers call “basis units”, which is technically required by thestandards.

Multi-user Concurrent Consistency is provided.

An Architectural model is provided including:

-   -   A Protected system model;    -   A Equipment abstraction model;    -   A Cause of Overpressure abstraction model;    -   A Document database;    -   A Maintenance database;    -   An Automated Workflow model;    -   A Signoff model;    -   A Version Control model;    -   A Permissions model;    -   Worksheets and Units;    -   An Engineering Worksheet Model, versions maintained (The        worksheets, links, and workflow supports the overall process of        PRD safety auditing;    -   Dependency links (all units, protected systems, equipment,        calculations, documents);    -   Unique “workflow architecture”—Controls evaluation of        worksheets;    -   A “State change” model—business object poster records last        person who changed record and when, changes force object into        state open;    -   An Automated Inlet/Outlet loss calculations Workflow Management;        and    -   Multi-user/Concurrent Web access control.

Object Models: the Evaluation System provides a user interface for themanipulation of data relating to plants and the devices they contain,and for management of the workflow related to relief device complianceauditing. The data is structured according to a set of persistentclasses, instances of which are stored in the database. The persistentobjects are related according to the following schematic, which isdescribed below.

PSM maintains data on one or more plants, such as a Greenwood Upstreamplant or a Site #4 plant, for example. Each plant contains one or moreprocesses, such as an Acetic Acid process and a Cellulose Fibre process,for example. Each process contains one or more protected systems, suchas a Glycol Heater protected system and a Vapor Scrubber protectedsystem, for example. Each protected system contains one or more devices,such as a Heat Exchanger and a Relief Valve (in a particular order), forexample. In the field data previously studied, protected systems usuallyhave an iso-piping drawing.

Each device typically belongs to one or more protected systems. Forexample, a heat exchanger can belong to separate input and outputprotected systems. Each device is of a particular type, such ascompressor, pump, vessel, block valve, control valve, relief valve, heatexchanger, etc., for example. The device type determines the values thatare associated with each device, either via user input or via connectionto an upstream device, for example. The device type also determines theworksheet calculations and rules that are used to attempt to certify adevice pursuant to compliance auditing (such as how to compute therequired orifice area for a relief valve from the device operatingvalues, for example).

Each protected system can have one or more hazard analysis scenarios,such as Cleaning and Fire, for example. Each scenario can have one ormore hazard cases, such as Blocked Flow or Fire Vapor Generation, forexample. Each type of hazard case determines the worksheet calculationsand rules that are used to compute the derived values used forcompliance auditing (such as required orifice area, for example),according to engineering standards that are applicable to the hazardcase. Each hazard scenario determines summary values for all its cases(such as by using sum or maximum, for example). Each protected systemdetermines summary values for all its hazard scenarios, and checks therelevant compliance rules from the engineering standards.

Devices can also have one or more maintenance records, which record themaintenance history of a device. This data can then be used duringcompliance auditing.

Audits can be conducted on plants, processes, or protected systems. Eachaudit maintains information on the compliance status of all the devicesunder purview by the audit. Each audit guides the auditors through theworkflow required to perform inspections, certify the results, andsign-off the audit.

Whenever an audit is moved to a new workflow status, a history record iskept on who made the change, when, and why. In addition, when an auditstatus is changed, copies of all the PSM reports relevant to the statuschanged can be saved in the document repository in non-proprietary HTMLformat, for example, so they may be viewed at any time in the future.

Evaluation System Operation and Usage of a Preferred Embodiment

This section describes the various functions and features of theEvaluation System in the perspective of user interactions and operationsfor the preferred embodiment. As such, this section both describesvarious input/output capabilities along with the correspondingEvaluation System functionality.

Note that although the system has been described utilizing varioussubsystems, as shown in FIG. 1, the actual organization of the variousfunctions below is somewhat arbitrary. The subsystems shown FIG. 1 areused for convenient categorization and to utilize commercially availableapplications, but the actual implementation of these functions intohardware and/or software is not critical, as various hardware andsoftware configurations can be utilized to achieve the same results, andsome combinations of functions may be implemented across the boundariesshown in FIG. 1.

Accordingly, referring to FIG. 1, and using the preferred embodiment,the server 3 is utilized to provide information, via the Internet, to aweb browser application running on a user computer. The user thenprovides updated information to the System 1 using the browser runningon the user computer, via the Internet, to the reception subsystem 4,which then routes the information to the storage subsystem for storing.Additional subsystems (e.g., report generation 7 and/or assessment 6)may also get the updated information, and/or various user commands, viathe reception subsystem. Thus, the user can control various aspects ofthe system, and add updated information, as described in more detail,below.

FIGS. 8A through 8X of the parent U.S. Pat. No. 7,617,013 filed on Dec.17, 2004, and incorporated by reference, show screen shots of a numberof the functions described below, for a contemplated commercialembodiment of the System, as they might be seen by a user of the system,displayed by a web browser on the user computer.

The assessment subsystem 6 is utilized to provide the various assessmentand auditing reviews of the process system being evaluated, while thereport generation subsystem is used to generate support documentations,as necessary, to provide a proper paper trail or explain results, asneeded. Accordingly, the various features and capabilities describedbelow can be allocated to the various subsystems consistent with thisoverall framework.

The Evaluation System web pages and display information, which areserved by the server to the user, are designed to use one or more commonelements combined according to one a number of different styles. TheEvaluation System uses the common edit boxes, checkboxes, dropdowns, andradio buttons. Their appearance may depend upon the web browser used.Action buttons are specially marked links. As you pass your cursor overa link, its marks change. Menus are composed of action buttons arrangedhorizontally, vertically, or in dropdown menus.

Page access is also controlled in the preferred embodiment of theEvaluation System. Users can be given specific access privileges thatgovern what pages can be viewed, and what actions are available on thosepages. Furthermore, only the Login page can be bookmarked. No other theEvaluation System web pages can be revisited once a browser window isclosed.

In a preferred embodiment, Italic links are used initiate actions thatmake changes to the database, and generate confirmation dialogs whenpicked. Non-italic links are used for navigational purposes, and do notgenerate changes to the database.

The Evaluation System of the preferred embodiment uses small icons forindicators and actions. A short description of an icon's function isdisplayed when a cursor is paused over the icon for a second or two. Adescriptive catalog of the icons called Common Icons used in theEvaluation System is available.

There are at least two types of dialogs used in the preferredembodiment: browser dialogs and application dialogs. Browser dialogs areused for simple confirmations. The application dialogs are pop-upwindows that are small web pages with controls that are used to collectdata or perform special operations for their parent pages.

The Evaluation System, such as the example embodiment having the exampleProthos Framework architecture as shown in FIG. 10, can be utilized toperform evaluations and audits for a number of industrial systems, suchas petroleum plants and other process plants, using the project workflowmodel shown in FIG. 9.

However, an industry that can particularly benefit from applying theprinciples and features of the Evaluation System is the nuclearindustry, which requires the use of pressurized fluids both for coolingsystems, and for thermal transfer of reactor heat to power generatingsystems. FIG. 8 shows an example physical structure implementation ofsuch a use.

The nuclear industry is required to meet a number of regulatorystandards in order to obtain the desired operating licenses. Forexample, the Nuclear Regulatory Commission (NRC) licenses allcommercially owned nuclear power plants that produce electricity in theUnited States. Standard Technical Specifications (STS) are published foreach of the five reactor types as a NUREG-series publication. Plants arerequired to operate within these specifications. The NRC's regulationsare found in Chapter I of Title 10, “Energy,” of the Code of FederalRegulations (CFR). Chapter I is divided into Parts 1 through 199.Improved Standard Technical Specifications (STS) were developed based onthe criteria in the Final Commission Policy Statement on TechnicalSpecification Improvements for Nuclear Power Reactors, dated Jul. 22,1993 (58 FR 39132). This policy statement was subsequently codified bychanges to Section 36 of Part 50 of Title 10 of the Code of FederalRegulations (10 CFR 50.36) (see also 60 FR 36953, Jul. 16, 1995). STS,Revision 3 is continuously modified by NRC incorporating approvedgeneric changes known as “Travelers”. NRC encourages licensees toupgrade their technical specifications consistent with the criteria inthe policy statement and conforming, to the practical extent, toRevision 3 with incorporated Travelers to the improved STS.

In order to construct or operate a nuclear power plant, an applicantmust submit a Safety Analysis Report. This document contains the designinformation and criteria for the proposed reactor, and comprehensivedata on the proposed site. It also discusses various hypotheticalaccident situations and the safety features of the plant that wouldprevent accidents or lessen their effects. In addition, the applicationmust contain a comprehensive assessment of the environmental impact ofthe proposed plant. A prospective licensee also must submit informationfor antitrust reviews of the proposed plant.

When an application to construct a nuclear plant is received, the NRCstaff determines whether it contains sufficient information to satisfyCommission requirements for a detailed review. The NRC staff thenreviews the application to determine whether the plant design meets allapplicable regulations (10 CFR Parts 20, 50, 73, and 100).

The NRC may approve and certify a standard nuclear plant design througha rulemaking, independent of a specific site. The design certificationis valid for 15 years. An application for a standard designcertification must contain proposed inspections, tests, analyses, andacceptance criteria (ITAAC) for the standard design. The applicationmust also demonstrate how the applicant complies with the Commission'srelevant regulations.

The safety review of the application is based primarily on theinformation submitted by the applicant under oath or affirmation. Anapplication must contain a level of design information sufficient toenable the Commission to reach a final conclusion on all safetyquestions associated with the design. In general terms, a designcertification application should provide an essentially complete nuclearplant design, with the exception of some site-specific design features.

The application presents the design basis, the limits on operation, anda safety analysis of structures, systems, and components of the facilityas a whole. The scope and contents of the application are equivalent tothe level of detail found in a Final Safety Analysis Report for acurrently operating plant. The NRC staff prepares a Safety EvaluationReport that describes its review of the plant design and how the designmeets applicable regulations.

The review process for new reactor designs involves certifying standardreactor designs, independent of a specific site, through a rulemaking(Subpart B of Part 52). This rulemaking can certify a reactor design for15 years. Design certification applicants must provide the technicalinformation necessary to demonstrate compliance with the safetystandards set forth in applicable NRC regulations (10 CFR Parts 20, 50,73, and 100).

After the initial license is granted, the license may be amended,renewed, transferred, or otherwise modified, depending on activitiesthat affect the reactor during its operating life.

Furthermore, the licensing process for research and test reactors isconducted in accordance with the requirements in 10 CFR Part 50 forClass 104 licenses.

But traditionally, the licensing and regulatory process involved the useof detailed spreadsheets and divers databases and paper documentationthat made it difficult to evaluate various failure scenarios andequipment modifications. The interactions of changes in one part of thecooling or power systems with other parts could not be easily modeledand evaluated. Thus, risk assessment and modification impacts weredifficult to conduct, and prone to errors.

However, the use of an evaluation system as disclosed herein, and inparticular the use of the iPRSM paradigm, can greatly improve theevaluation of the pressure systems of a nuclear power plant. The impactof modifications and changes in one part of the cooling or power systemscan be easily modeled by the software to determine any safety impacts inthe overall system. The evaluation system can be used to determinewhether proposed designs, or changes to existing designs, meet therequired licensing requirements and support the design certificationprocess.

To adapt iPRSM for use in the nuclear industry, the iPRSM equipmentdatabases are populated with the safety and power subsystem devices (andtheir operational parameters) that are used in these subsystems. Inparticular, where water is the working fluid, the equipment (piping,safety valves, etc.) that are used for this fluid are provided in thedatabase. Basic computational formulas need not be changed, as the iPRSMsoftware includes those basic physical mathematical formulas necessaryto do the basic computation. Safety margins unique to the nuclearindustry will also be entered for use in the analysis.

Desired reports specifically adapted to the design, licensing, auditingand certification process are generated using the iPRSM documentationtools. In this manner, the entire process from design to certificationto recurring licensing can be supported by iPRSM. Once the database ispopulated with the appropriate equipment, iPRSM becomes a knowledgecapture and evaluation tool for use in nuclear plant design andcertification, evaluating rules changes, equipment changes, and otherevaluation procedures that can then be accomplished in an economical andpractical manner. The use of a tool like iPRSM to capture suchinformation and support such evaluations is likely to become eitherimplicitly, or explicitly, mandatory.

Evaluation System Example Features of the Preferred Embodiment

Various collections of data require different display page types. Thefollowing types of pages are used in the Evaluation System:

Browsers display a list of one or more items in a table. Browsersusually have controls to select and sort the displayed items, andcontrols to scroll through results too numerous for display on a singlepage. Each row contains data for one item, a way to zoom to detailsabout that item, and in some cases, controls to operate on it.

Viewers display details for an item, sometimes for editing. A viewer mayincorporate a browser if its item can contain other items (e.g., a plantcontains units).

Pop-Up Dialogs are small pages that pop up from a browser or viewer toallow special data entry, selection, or sequencing operations to beperformed for an item.

Report Menus are a collection of links to individual reports, in somecases with controls for selecting and sorting report data.

Reports display details for an item, suitable for printing by a browserapplication.

There are typically no controls on report pages, so a browser's Backbutton can be used to return to a report's previous page.

Using the Database: the Evaluation System's database is designed to beused by many users at once, in some cases over a network connection thatcannot be trusted to be available from page to page. These factors makeusing the Evaluation System database slightly different from usingdesktop-based databases.

Because of the nature of the connection between a user computer and theEvaluation System server, the data displayed on a user computer is asnapshot of the data held for that item.

When a user makes changes to the data, the changes are not transmittedto the database until the user selects Post, Done, or anotheroperational link. Using the browser's Back button typically will notsave the changes to the database. However, most application buttons oroperational links that cause a new page to be loaded attempt to save anychanges that have been made to the current page before displaying thenew page.

Other users may request the same page as a particular user, and thusreceive their own snapshots, but only one person can save changes at atime. If another user saves changes to the other user's snapshot first,the user will be unable to save the changes to his snapshot, but willhave to refresh the snapshot first to update his data, and then modifythe newly-updated data.

As an Example: A user requests the Evaluation System to view data abouta valve (by clicking on a link or button displayed by a browser, forexample). The Evaluation System packages it up and sends the user awebpage via the server. Then the telephone rings, and the user dealswith the call. In the interim, another user else retrieves a snapshot ofthe data for the same valve, makes changes to their snapshot, and savesthe changes successfully.

After the call, the user attempts to change some of the valve's data (byinputting data into a web form, for example) and wants to save it backto the database (via the reception subsystem to the storage subsystem).However, the Evaluation System detects that the data has changed sincethe time the user retrieved it, and refuses the change, displaying anerror message instead.

In the error message is a link to Reload the page the user was viewing,which, when selected, presents the user with the valve's updated data,and the user must now re-enter the desired changes. A small pop-upwindow with the word “Posting . . . ” comes and goes as the user Posthis changes. In cases where changes cannot be saved, this window expandsto display an error message and suggest remedial actions.

Dates and Times: Because the Evaluation System is designed for use ininternational environments, all dates and times preferably use theISO-8601 format: yyyy-mm-dd [hh:mm:ss]. Example: 2003-10-31 [17:18:26]

A user can run multiple application windows in cases where the userneeds to refer to one or more other pages while working. The EvaluationSystem logo can be used to open a new Evaluation System Main Page,allowing multiple pages to be simultaneously browsed for multitasking.

For smart navigation, the user can pick Post and then right-click thebrowser Back button to save changes and safely navigate directly to anypage in the navigation history list. The user can pause the cursor overany icon in a browser window to view an instructional popup tool tip.

Overview

Menu and Action links are marked with Common Navigation Icons, whichchange as the cursor moves over them. Pick the link to take the action.Use these icons to page through multiple items in groups. From left toright, they represent First, Previous, Next and Last items. They appeargrayed when paging is not possible for the current set of items. SelectPost to Save changes to database.

Additional features include viewing a drawing in a separate window;viewing list of associated documents; and viewing a menu of associatedreports. Furthermore, a variety of icons are provided which are linkedto various functionality, including: Equipment; Equipment Pipe Fittings;Equipment Maintenance History; Equipment Findings; Protected Systems;Protected System Contingency; Piping Losses; Add; Add Under; DeleteRecord—Delete the record from the database; Archive Record—Archive therecord so that it does not appear in views on the current database;Re-sequence—Access a re-sequencing popup and change the order of itemsin a list; Evaluate—Resolve outstanding calculations; Select File—selectindicated file for use; Send Mail—Send email to another applicationuser; Erase—Clear the value in a field; Clock—Enter a current timestampin a date/time field; Select Entries—Open a page from which to selectone or more entries to fill a field; Parameter Information—Accessparameter information; Create a Parameter Link View or Edit a ParameterLink View or Edit a Bad Parameter Link; Select Orientation Angle; Ok;Not Ok; Locked by another user; Locked by current user; Mail Sent—Emailsent.

A quick-reference summary of the web application workflow andfunctionality includes the following list of functions:

-   -   Log in/out    -   Add a plant    -   Add a unit to the plant    -   Add equipment to a unit    -   Add protected systems for a unit    -   Add contingency scenarios for a protected system    -   Evaluate piping losses for a contingency scenario    -   Evaluate contingency scenarios for a protected system    -   Check and sign off a protected system    -   Check equipment for a unit    -   Check and sign off a unit    -   Check and sign off a plant

The above functions are described in more detail in the followingexamples:

Logging in: A user points his web browser to the appropriate websiteURL, enters the appropriate Login ID and Password, and picks theappropriate Login link to access the Evaluation System main page.

Logging out: On the main page, the user picks the Logout link. Merelyclosing the browser windows may not provide a secure logout under someoperating systems.

Adding a plant: On the Evaluation System main page, pick the Add a Plantlink and confirm to create a plant and access the add plant view. Entera new Plant Name, a new Plant Owner, and select a template from the NewPlant Template dropdown. Pick the Add Plant link and confirm to access ablank plant view in which to enter detailed plant information. Enteradditional plant details as required, then pick Post.

Adding a unit to the plant: In the plant view's Plant Units table, pickthe Add Unit link and confirm to create a unit and access a blank unitview in which to enter detailed unit information. Enter a Unit Name,Location, and Contact information. Pick Post.

Adding equipment to a unit: In the unit view, pick the Browse Equipmentlink to open the equipment browser.

Add one or more pieces of equipment: For each piece of equipment, pickthe Add New Equipment link, enter a unique identifying string in the ID#box, then pick OK to create the new piece of equipment and access ablank equipment view in which to enter new equipment information. Selecta device type from the Device Type dropdown. A parameter panelappropriate to the device type will open. Enter equipment details andparameters. Pick Add More Equipment from the Other Functions dropdown torefresh the equipment view and add more equipment, or pick Done toreturn to the equipment browser. A basic protected system requires arelief device, a piece of protected equipment, and an overpressuresource.

For relief equipment, in the equipment view, also use the add icons iconto add associated equipment, pick the Piping & Fittings link to accessthe equipment piping browser and view, edit, and evaluate inlet andoutlet piping and fittings. Pick the Piping Losses link to access theequipment piping losses browser and view piping losses information foreach contingency scenario that is applied to a piece of protectingequipment's protected system. Pick the Findings & Deficiencies link toaccess the equipment findings view and enter findings and deficiencydetails.

Adding a protected system for a unit: In the unit view, pick theProtected Systems link to access the protected system browser. Pick theAdd System link and confirm to create the protected system and accessthe protected system view. Enter a System Name and Default OVP Category,and select a value from the Pset Basis dropdown. Pick the Add Equipmentlink in any of the System Relief Equipment, System Protected Equipment,OVP Sources, or Ancillary Equipment tables to access the link equipmentview and select equipment of the appropriate type to link to theprotected system. Note that only equipment already added to the unit andnot already used in another protected system is available to be linkedto a protected system. From the Other Functions dropdown, pick Add NewSystem to refresh the page and add another protected system, or pickDone to return to the protected system browser.

Adding a contingency scenario for a protected system: From theContingency Scenario table in the protected system view, pick the AddNew Scenario link and confirm to add a scenario and access thecontingency scenario view. From the Overpressure Type, Hazard Typeand/or Flow Type dropdowns, select OVP type, hazard type, and/or flowtype. A parameter panel appropriate to the scenario will open. Enterscenario parameters then pick the Evaluate Scenario link or a Calculatoricon. Correct problems described by any warning messages, and repeatevaluation until the scenario is successful. Pick Done to return to theprotected system view, or pick Piping Losses to access the piping lossesview and proceed with evaluating and signing off piping losses.

Evaluating and signing off piping losses for a contingency scenario: Toaccess the piping losses view, pick the Piping Losses link in thecontingency scenario view or pick a piping losses icon in theContingency Scenarios table of the protected system view. Pick theUpdate Piping and Losses link to update piping parameters to currentvalues and open parameter fields for editing. Pick the Evaluate Scenarioand Update Piping and Losses link if the scenario has not yet beenevaluated to evaluate and open parameter fields for editing. Editparameter values as required and pick a calculator icon to evaluatepiping losses until the result is satisfactory. Pick the Signoff Losseslink to sign off on piping losses. Piping status will change to “OK”.Pick Post to post changes or Done to post changes and return to theprevious page. Evaluating, signing off, and un-checking a contingencyscenario for a protected system. In the contingency scenario view editparameter values as required.

Optionally, pick an unlink icon to open the parameter dependencyworksheet and specify a parameter dependency for the selected value.Pick the Evaluate Scenario link or a calculator icon to evaluate thescenario. Scenario status will change from “Open” to “Comp” when thescenario is adequate. Edit parameters and evaluate as required until theresult is satisfactory and the scenario status is “Comp”.

Once a scenario's status is “Comp”, pick the Scenario Signoff link tocheck the scenario and its piping loss calculations. Scenario statusshould change from “Open” to “Checked”. If status remains “Open”, pickthe Mitigate link to resolve open issues.

Optionally, from the Other Functions dropdown, pick Un-check Scenario tochange the status of all scenario objects to “Open” and begin theevaluating and checking process anew. Scenario objects include theprotected system and its equipment, the scenario, and its piping losses.

Checking, signing off, and un-checking a protected system in a unit: Inthe protected system view, pick the Check System link to check allcontingency scenarios and their piping losses, and all relief deviceswithin the system. If protection is adequate, the system status willchange to “System Ok”. Pick the System Signoff link to signoff on theprotected system.

Optionally, from the Other Functions dropdown, pick Un-check System tochange the status of all objects in the system to “Open” and begin thechecking and evaluating process anew. These objects include theprotected system and its equipment, the contingency scenarios and theirpiping losses.

Checking equipment: Once all protected systems have been checked and areof status “Ok”, pick the Check Equipment link in either the: unit viewequipment browser or protected system browser. The status of allequipment within the unit will change to “Checked”.

Signing off and un-checking a unit: Once all protected systems within aunit have been checked and are of status “Ok”, and all equipment hasbeen checked and is of status “Checked”, pick the Unit Signoff link inthe unit view to signoff on the unit.

Optionally, from the Other Functions dropdown in the unit view, pick theUn-check Unit link to change the status of all objects within the unitto “Open” and begin the checking and evaluating process anew. Objectswithin the unit include all equipment, protected systems, contingencyscenarios, and piping losses.

Signing off and un-checking a plant: Once all units within a plant havebeen checked and are of status “Ok”, in the plant view, pick the PlantSignoff link to signoff on the plant.

Optionally, from the Other Functions dropdown in the plant view, pickthe Un-check Plant link to change the status of all objects within theplant to “Open” and begin the checking and evaluating process anew.Objects within the plant include all units, equipment, protectedsystems, contingency scenarios, and piping losses.

Extra-Workflow Procedures: Managing unit, equipment, and protectedsystem graphics Process and instrumentation drawings for systems can beuploaded and viewed in the Evaluation System in a number of thefollowing formats: .gif, .jpeg, .png, .tif, pdf, and NCSA image map. AnNCSA link map should use the Evaluation System equipment ID#s toidentify its components.

The unit P&ID drawing browser can be used to view and sort the drawingslist for a unit locate, add, and delete drawings access the unit P&IDdrawing popup access the unit P&ID drawing editor. To view a unit P&IDdrawing, do one of the following: In the unit P&ID drawing browser, picka drawing name. In the equipment view, pick the P&ID Drawing link. Inthe protected system view, pick the drawing icon for a piece of reliefequipment. In the unit P&ID drawing popup or the unit P&ID drawingeditor, pick View Image from Other Functions to view an enlarged versionof the drawing in a new window. Use the unit P&ID drawing editor to editdrawing name and version, and upload or download drawings or image maps.Use the equipment P&ID drawing selector to create, replace or remove alink between a piece of equipment and a P&ID drawing.

Use the equipment ISO drawing editor to upload, download, or delete anISO drawing. To view an ISO drawing, do one of the following: In theequipment view, pick the ISO Drawing link; In the equipment ISO drawingpopup or the equipment ISO drawing editor, pick the View Image link toview an enlarged version of the drawing in a new window.

Use the system sketch editor to upload, download, or delete a systemsketch. To view a system sketch, do one of the following: In theprotected system browser, pick a sketch icon; In the protected systemview, pick the System Sketch link; In the system sketch view, pick theView Image link to view an enlarged version of the sketch in a newwindow.

Managing unit, equipment, and system documents: Documents can beuploaded and viewed in the Evaluation System in single or multiple filebundles in one or more of the following formats: .awp, .bkp, .doc, .xls,.pdf, .bmp, .dwg, .gif, .jpeg, .png, .tif, .html, .zip, and .txt. TheEvaluation System handles documents for units, equipment, and protectedsystems in parallel fashion.

Use document browsers to view lists of all documents for a unit, pieceof equipment, or system access the document views. Use the documentviews to view lists of all versions of a document for a unit, piece ofequipment, or system enter or edit document details or upload newdocument versions download a document for editing access the documentversion views. Use the document version views to view lists of all fileswithin a version of a document for a unit, piece of equipment, orsystem; enter or edit version details; open individual files within aversion of a document; and access the version uploaders. Use the versionuploaders to locate and select files to upload as versions of a documentfor a unit, piece of equipment, or system.

Managing worksheets: To view a selected worksheet, pick the Worksheetlink in one of the plant view, equipment view, protected system view, orcontingency scenario view piping losses worksheet. Use the worksheetview to update worksheets individually, or use the worksheet updater toupdate multiple worksheets at a time. To access the worksheet updater ata selected level, from the Other Functions dropdown, use Update W/Sheetsin the plant view to update all worksheets in the plant (available onlyto System Administrators); use unit view, equipment browser, orprotected system browser to update all worksheets in the unit; useequipment view to update all worksheets related to the piece ofequipment; use protected system view to update all worksheets related tothe system (updating worksheets from the protected system view is theeasiest way to update the protected system, its equipment and its pipingsimultaneously); use contingency scenario view to update all worksheetsrelated to the scenario; use piping losses view to update all worksheetsrelated to the piping losses.

Managing revisions: Use the revision browser and revision view tomaintain revision control over changes to protected systems. Use therevision browser to view lists of protected systems and their revisionnumbers for a plant or for a unit within a plant locate protected systemrevisions by search criteria access the revision view. Use the revisionview to: view and update revision details for a protected system; changerevision stage; or add a revision to a protected system.

Managing tasks: Use the tasks browser and tasks view to manage userassigned tasks. To access the tasks browser, on the main page, pickTasks Queue from the Other Functions dropdown. Use the tasks browser to:view the tasks queue for a user or all users; download the tasks queueto Excel; locate tasks by search criteria add new tasks; or access thetasks view. Also use the tasks view to view, enter, or edit taskdetails; or email task information to users

Managing Reports: Use the report browser to locate and generate anyreport, or use the context-sensitive Report link on any page to accessthe corresponding reports view. Use the report browser to locate andgenerate any report without navigating to the relevant application page.

To access the report browser, on the main page select Browse Reportsfrom the Other Functions dropdown.

Use the context-sensitive Report links throughout the Evaluation Systemto access the relevant reports view, then use the reports view to locateand generate the required report.

Tutorials

Various online tutorials are provided for guiding a user. The tutorialsare described below. These tutorials provide an example of how toutilize the Evaluation System for analyzing a plant design in asimplified manner. the Evaluation System supports the much more complexconfigurations of actual plant designs, of course, and thus actualcapability is not limited by these examples, which are provided forillustrative purposes only.

Creation Tutorial: This tutorial guides the user through the stepsinvolved in creating and checking a simple one-unit plant containing acompressor, a vessel, and a pressure relief valve.

The steps in this tutorial are: add a new plant to the database; add anew unit to the plant; add new equipment to the unit; add a compressorto the unit; add a vessel to the unit; add a PRV to the unit; add pipingand fittings to the PRV; add a protected system to the unit; link theequipment to the protected system; add a contingency scenario calculatepiping losses; check and sign off on the protected system; sign off onthe unit and plant.

Mitigation Tutorial: This tutorial guides the user through the stepsinvolved in changing a compressor and then mitigating the effects ofthat change throughout a standard demonstration plant.

The steps in this tutorial include: create a standard demonstrationplant; change a compressor; re-check contingency scenarios affected bythe compressor change; change a relief valve to mitigate the effects ofthe compressor change; re-check the system to determine the effects ofthe relief valve change; and complete the checking and sign-off process.

Fittings Tutorial: This tutorial guides the user through the stepsinvolved in setting up the inlet and outlet piping and fittings for apressure relief device. The steps in this tutorial are: create a simpleshop air plant; add a relief valve navigate to the piping and fittingseditor; add, configure, and evaluate inlet fittings; and add andconfigure outlet fittings.

System Detailed Operation

User Interface Pages: User Interface Pages are used for user interactionwith the Evaluation System, and such pages include:

-   -   System Login page;    -   System Logout page;    -   The Main page;    -   Plants page;    -   Units page;    -   Equipment page;    -   Protected Systems page;    -   Contingency Scenarios page;    -   Worksheets page;    -   Devices page;    -   Hazards page;    -   Pipe Fittings page;    -   Tasks Queue page; and    -   Browse Reports page.

Some of these various pages are described in more detail below:

Login Page: Use the login page to: log in to the Evaluation System; logout from the Evaluation System; and for accessing the systemadministrator login page. A Logout Page is the preferred way to log offthe Evaluation System.

The Main Page: The main page is used to locate plants; sort the plantlist view; add and delete plants; generate plant and other reports; andprovide access to:

-   -   Evaluation System handbook;    -   on-line tutorials, user information and preferences;    -   multi-tasking interface;    -   document library (for accessing Evaluation System documents,        site documents and industry documents);    -   worksheet library (for accessing worksheet views or browsers        for: plants, device types, pipe fittings, protected systems,        scenario hazards, scenario standard OVP types, and piping        losses);    -   reports browser;    -   send mail to site users utility;    -   Tasks queue browser;    -   site load graph (for generating and viewing graphs of        transactions, unique users, trouble messages, and locks denied        over a selected recent time period); and    -   site administration page.        Visitor-level users can only access a restricted, read-only        version of the Evaluation System main page.

The Multi-Tasking Interface for access to the Evaluation System'smultitasking utilities and session. Options include Other Functionsincluding functions of: a Document Library to access the documentlibrary and view Evaluation System documents, site documents, andindustry documents; A Worksheet Library to access the worksheet libraryand view and manipulate plant and protected system worksheets and browsepipe fitting, hazard, and piping loss worksheets and standard OVP types;Browse Reports to access the reports browser and generate and printreports on all aspects of the Evaluation System, and to provide aread-only interface to Evaluation System reports for users withVisitor-level access; Send Mail for Users to send email to EvaluationSystem users; a Tasks Queue to access the tasks queue browser and view,sort and edit tasks lists for System users; a Site Load Graph to accessthe site load graph and view the graphs of transactions, unique users,trouble messages, and locks denied over a selected recent time period;and Site Administration to access the site administration page andconduct site administration functions (only visible to SiteAdministrators).

The Plants Page: is used for providing links to the following functions:

A Plant View function for: viewing, entering, or editing plantinformation; accessing the unit view for units within the plant;creating or deleting units; viewing unit P&ID drawings, equipment, andprotected systems; accessing and updating plant worksheets; viewing,entering or editing plant notes; un-checking or re-checking a plant;signing off on a plant that has been checked; and exporting a plant.

A Plant Standard OVPs function for: viewing and sorting a list of plantstandard OVP contingency types; adding or deleting an OVP contingencytype; adding, sequencing or deleting hazard types for an OVP contingencytype; and editing standard notes for an OVP contingency type.

An OVP Standard Notes function for: viewing to enter or edit standardnotes for an overpressure contingency scenario. Notes entered here canbe applied to contingency scenarios using the scenario note selector.

An Export Plant function for: browsing available plant template documentpackages and plant document packages in the Plant Template area of therepository; adding a plant template document or plant document to thePlant Template area of the repository; selecting a plant templatedocument or plant document from the Plant Template area of therepository to which to export a plant template document or plantdocument for the current plant; viewing a selected document from thePlant Template area of the repository; viewing current and previousversions of the current plant's worksheet; generating a plant templatedocument or plant document for export; and/or exporting a generatedplant template document or plant document to the Plant Template area ofthe repository.

An Import Plant function for: browsing available plant template documentpackages and plant document packages in the Plant Template area of therepository; adding a plant template document or plant document to thePlant Template area of the repository; and/or selecting, viewing andimporting a previously exported plant template or plant that has beenuploaded and saved as a plant template document package or plantdocument package in the Plant Template area of the repository.

A Plant Unit Styles function for: selecting a default units style forall values within the plant; an OVP Type Sequencer function for:changing the order in which OVP contingency scenarios are considered anddisplayed; an OVP Hazard Sequencer function for: changing the order inwhich OVP contingency hazards are considered and displayed; a Plant orUnit Re-check for rechecking all Open systems in a plant or unit; aPlant Reports function for: creating plant-related reports; a PlantDelete function for: confirm deletion of a plant where access isrestricted; a Plant Freeze/Thaw function for: freezing and thawingplants during plant export and import operations; and an Add New PlantPopup function for: creating a new plant and entering basic plantinformation.

A Units Page provided with links for the following functions:

A Unit View function for: viewing, entering or editing unit information;accessing unit-related information in the unit equipment browser, P&IDdrawings browser, protected systems browser, or the document browser;accessing the unit worksheet updater; checking unit equipment;re-checking a unit, un-checking a unit, or signing off on a checkedunit; entering or editing unit notes

A Unit P&ID Drawing Browser function for: locating, viewing, adding ordeleting process and instrumentation drawings for a unit; a Unit P&IDDrawing Popup function for: viewing an uploaded unit drawing if an NCSAlink map has been uploaded, to access details for equipment in the unit;a Unit P&ID Drawing Uploader function for: selecting and uploading aunit P&ID image or link map to the System server; a Unit DocumentsBrowser function for: accessing, editing, adding or deleting documentsfor a unit; a Unit Document Upload function for: locating, selecting anduploading files as versions of unit documents; a Unit Reports functionfor: viewing and printing unit-related reports and drawings; and A UnitDelete function for: confirming deletion of a unit in a plant.

A Unit P&ID Drawing Editor function for: viewing a unit P&ID drawing orlink map; adding a new unit P&ID drawing or link map; uploading ordownloading a unit P&ID drawing; uploading or downloading a unit P&IDlink map; and accessing equipment details in a unit P&ID link map.

A Unit Document View function for: viewing, entering or editing detailsfor a unit document; downloading a unit document for editing;designating or viewing a launch file for a multiple file unit document;and adding, viewing or deleting unit document versions.

A Unit Document Version function for: viewing, entering, or editing,document version details; uploading or downloading a document version;designating or viewing launch files for multiple file documents; andopening individual files within a document version.

A Unit Equipment Data Import function for: importing data for a newpiece of equipment (equipment data should come from a document alreadyuploaded to the Evaluation System through the Document Uploaderfunction), and a Unit Equipment Data Export function for: exporting unitequipment data to a spreadsheet (such as MS Excel) for editing.

An Equipment Page provided with links for the following functions:

An Equipment Browser function for: viewing an equipment list for a plantor a unit within a plant; locating equipment by ID#, type, system, orstatus; sorting the equipment list; viewing equipment details; adding ordeleting equipment; accessing protected system information; initiatingan equipment check; importing or exporting equipment data; accessing theequipment redbook editor; updating equipment worksheets; and accessingrevision control history.

An Equipment View function for: viewing, entering, or editing equipmentdetails; adding equipment to a unit; managing associated equipment;accessing equipment worksheets, maintenance reports, and documents;viewing and uploading ISO drawings; viewing and selecting P&ID drawings;un-checking equipment and updating worksheets; and for protectingequipment and accessing piping and fittings, piping losses, and findings& deficiencies information.

An Equipment P&ID Drawing Select function for: locating, viewing orediting a unit P&ID drawing; and creating, replacing or removing a linkbetween a unit P&ID drawing and the equipment currently displayed in theequipment view.

An Equipment ISO Drawing Popup function for: viewing an uploaded ISOdrawing, and use the Equipment ISO Drawing Uploader function for:selecting and uploading an ISO drawing to the Evaluation System server.

An Equipment ISO Drawing Editor function for: viewing an equipment ISOdrawing; uploading or downloading an equipment ISO drawing; and deletingan equipment ISO drawing.

An Equipment Associations function for: locating equipment to associate;accessing equipment details; creating an equipment association; andclearing an equipment association.

An Equipment Piping Browser function for: viewing inlet and outletpiping and fittings lists for a piece of equipment; adding or deletingpiping and fittings; accessing and editing piping and fittings details;re-sequencing inlet and outlet piping and fittings; accessing theequipment piping editor; viewing piping losses; viewing ISO and P&IDdrawings; evaluating piping and fittings; and updating piping andfittings worksheets and viewing or hiding worksheet informationmessages.

An Equipment Piping Editor function for: add, editing and deletingpiping and fittings for a piece of equipment; evaluating piping andfittings; accessing and editing piping and fittings details;re-sequencing piping and fittings; viewing piping losses; viewing ISOand P&ID drawings; and updating piping and fittings worksheets and viewor hide worksheet information messages and fitting notes.

An Equipment Piping View function for: viewing, entering, editing orevaluating inlet and outlet piping and fitting details; and adding newpiping and fittings.

An Equipment Piping Sequencer function for: changing the order in whichpiping and fittings are considered and displayed: for inlet, fromentrance to device; and for outlet, from device to exit.

An Equipment Redbook function for: viewing protecting equipment listsfor a unit; locating protecting equipment by ID#, system, or status;sorting the protecting equipment list; and viewing or editing redbookparameters for protecting equipment.

An Equipment Piping Losses function for: accessing piping lossesinformation for each contingency scenario that is applied to a piece ofprotecting equipment's protected system.

An Equipment Findings & Deficiencies function, for a piece of protectingequipment within a system, for: viewing, enter, or edit findingsinformation; creating, editing, sequencing, and deleting equipmentdeficiencies; accessing equipment worksheets; viewing ISO and P&IDdrawings; accessing piping and fittings or piping losses information;accessing maintenance information or equipment documents; accessingprotected system information.

An Equipment Deficiency Sequencer function for: changing the order inwhich deficiencies are displayed; and an Equipment Documents functionfor: viewing, entering, editing, adding or deleting documents for apiece of equipment.

An Equipment Documents View function for: viewing, entering or editingequipment document details; downloading a document for editing;designating or viewing a launch file for a multiple file document; andadding, viewing, or deleting document versions.

An Equipment Documents Version function for: viewing, entering orediting details for a version of an equipment document; uploading ordownloading an equipment document version; designating or viewing launchfiles for multiple file documents; and opening individual files within adocument version.

An Equipment Documents Uploader function for: locating, selecting anduploading files as versions of equipment documents; and an EquipmentMaintenance View function for: viewing, entering or editing recorddetails for maintenance reports.

An Equipment Maintenance function for: viewing maintenance history;accessing maintenance details; and adding or deleting maintenancehistory entries.

An Equipment Reports function for: viewing a variety ofequipment-related reports; and an Equipment Browser function.

A Protected Systems Page provided with links for the followingfunctions:

A Protected System Browser function for: viewing protected systems listsfor a plant or units within a plant; locating protected systems by nameor status; sorting the protected systems list; viewing protected systemdetails; adding or deleting a protected system; accessing revisionhistory information; initiating a unit re-check; and updating protectedsystem worksheets.

A Protected System View function for: viewing, entering or editingprotected system details; adding a new protected system to a unit;viewing, adding, editing or deleting links to relief devices, protectedequipment, OVP sources, and ancillary equipment; viewing relief orprotected equipment P&ID drawings; adding, applying, editing,re-sequencing or deleting contingency scenarios; uploading or viewing aprotected system sketch; accessing protected system documents; accessingor updating protected system worksheets; checking protected systemequipment or initiate a system-wide re-check; and signing off on aprotected system.

A Protected System Sketch function for: viewing an uploaded protectedsystem sketch, and if an NCSA link map has been uploaded, for accessingequipment details for the system.

A System Sketch Editor function for: uploading, downloading or deletinga system sketch; uploading, downloading, or deleting a system link map;and accessing equipment details for system link maps.

A System Sketch Uploader function for: selecting and uploading an imageor link map to the Evaluation System server and an Add Standard OVPs toSystem function for: setting defaults for standard OVP scenarios andadding the OVPs to a protected system.

An Impact Analysis function for: evaluating the consequences of updatingthe worksheets associated with the protected system to their currentversions. Updating the worksheets for a protected system can affect itsaudit status since a change in standards may make an existing systemnon-compliant. This function enables the impact of the worksheet updateto be evaluated without actually doing so.

A Link Equipment View function for: locating available relief equipmentand sort the available relief equipment list and for linking availablerelief equipment to a protected system.

A System Scenario Adjustor function for: marking contingency scenariosas applicable or not applicable by category for a protected system, andfor deleting contingency scenarios by category for a protected system;and a Scenario Sequencer function for: changing the order in whichcontingency scenarios are considered and displayed.

A System Scenario Notes function for: viewing, entering or editingcustom notes for contingency scenarios associated with a protectedsystem; selecting standard notes for contingency scenarios; and applyingand re-sequencing contingency scenarios.

A System Revisions Browser function for: viewing revisions lists for aplant or units within a plant; locating revisions by name, systemstatus, revision number, status, or stage, and/or the user for whichthey are queued; sorting the revisions list; and accessing revisiondetails.

A System Revision View function for: viewing protected system revisionhistory; and entering, editing and deleting protected system revisions.

A Send Revision Mail function for: emailing revision notices toEvaluation System users, and a System Impact Analysis function; and aSystem Documents Browser function for accessing, editing, adding anddeleting documents for a protected system.

A System Document View function for: viewing, entering or editing systemdocument details; downloading a document for editing; designating orviewing a launch file for a multiple file document; and adding, viewing,or deleting document versions.

A System Document Version function for: viewing, entering or editingdetails for a system document version; uploading or downloading adocument version; designating or viewing launch files for multiple filedocuments; and opening individual files within a document version.

A System Document Uploader function for locating and selecting files toupload as versions of system documents; a Protected System Reportsfunction for generating and viewing a variety of protectedsystem-related reports; and a Protected System Browser function.

A Contingency Scenarios Page provided with links for the followingfunctions:

A Contingency Scenario View function for: viewing, entering or editingcontingency scenario details; entering or selecting contingency scenarioparameters; calculating piping losses for a contingency scenario; andevaluating or signing off on a contingency scenario.

A Scenario Notes Selector function for selecting standard notes toattach to a contingency scenario; a Scenario Variable Dependencyfunction for viewing, creating, or editing dependency links betweencontingency scenario parameters and parameters in other worksheets; aScenario Piping Losses function for updating, editing, and computingscenario piping losses for each relief device to which the contingencyscenario is applied; a Piping Losses Worksheet function for updating,editing, and computing piping losses for a contingency scenario appliedto a single relief device; and a Contingency Scenario Reports functionfor generating and viewing scenario reports.

A Worksheets Page provided with links for the following functions:

A Worksheet View function for: viewing worksheets for plants, equipment,protected systems, contingency scenarios, and piping losses; selectingworksheet versions; accessing worksheet specifications; and viewingsource or object code for the worksheet.

A Worksheet Updater function for: generating and viewing a worksheetupdating plan; and updating worksheets to the most recently uploadedversions

A Units Style Selector function for: converting and displaying theselected value in a new units style. Note that only the display valuewill be changed, not the basis value used in calculations.

A Worksheet Variable Information function for accessing detailedinformation about a parameter; and a Worksheet Specification Viewfunction for viewing to access worksheet variables and worksheetcalculations in source or object code for plants, protected systems,and/or piping losses.

A Worksheet Reports View function for: generating and viewing worksheetvalues and worksheet specification reports for plants, equipment,protected systems, contingency scenarios and/or piping losses.

A Devices Page provided with links for the following functions:

A Device Worksheet Browser function for: accessing device worksheets andadding or deleting device worksheets; a Device Worksheet View functionfor: viewing device worksheet variables and worksheet calculations codefor System Administrators, and selecting a protection function for adevice; and a Devices Reports function for: generating and viewingdevice worksheet specification reports.

A Hazards Page provided with links for the following functions:

A Hazard Browser function for: accessing hazard worksheets; adding ordeleting hazards; and accessing default plant OVP contingencies.

A Hazard View function for viewing hazard worksheet specifications andhazard source or object code, and entering or editing hazard details; aHazard Reports function for: generating and viewing hazard reports; anda Default OVP Contingencies function for accessing default plant OVPcontingencies.

A Pipe Fittings Page provided with links for the following functions:

A Pipe Fitting Browser function for: viewing the pipe fitting typeworksheets list; accessing fitting worksheets; and adding and deletingfitting worksheets

A Pipe Fitting View function for: viewing fitting worksheetspecifications; viewing fitting source or object code; and entering orediting fitting details and specify defaults and width variance.

A Pipe Fitting Reports function for: generating and viewing fittingreports; and a Piping Losses Worksheets function for accessing pipinglosses worksheet specifications.

A Tasks Queue Page provided with links for the following functions:

A Tasks Queue Browser function for: viewing task lists for users;locating tasks by user, user role, or task status; sorting the tasklist; viewing task details; adding and deleting tasks; and downloadingthe task list to a spreadsheet (such as MS Excel).

A Tasks View function for: viewing, entering, or editing task details,and preparing task notices for email; and a Tasks Send Mail functionfor: emailing task notices to Evaluation System users.

A Browse Reports Page provided with links for the following functions:

A Reports Browser function for: selecting, generating, displaying andprinting Evaluation System reports, where the reports browser provides aread-only interface to System reports for users with Visitor-levelaccess; and a System Selector function for: selecting protected systemsfor use in the reports browser.

The Evaluation System supports at least three types of graphics fileswhich can be uploaded, viewed and edited. These graphics files includeunit process and instrumentation (P&ID) drawings, equipment isometric(ISO) piping drawings, and protected systems sketches. Various graphicsformats are supported (such as gif, jpg, png, tif and pdf, for example).

A fourth type of file, the NCSA link map, can be created and uploadedalong with unit P&ID drawings and protected system sketches. The NCSAlink map feature can be used to create hotlinks from the pieces ofequipment illustrated in a graphic to the equipment view to display eachpiece of equipment's details. An equipment P&ID drawing selectorfunction is provided to create direct links from pieces of equipment inthe equipment view to the unit P&ID drawing in which they areillustrated.

Once a unit P&ID drawing has been uploaded, direct links can be createdfrom the equipment view from each piece of equipment to the drawing inwhich it is illustrated.

The Evaluation System provides a document library for system-widedocuments, plus repositories for unit, equipment, and protected systemdocuments. The document library is preferably a read-only resource formost users. Only system administrators is typically permitted to upload,edit, or delete these materials.

The Evaluation System manages unit, equipment, and protected systemdocuments in parallel fashion. The Evaluation System documents can beuploaded, managed and accessed as: awp. bkp. doc. xls. pdf. bmp. dwg.gif. jpeg. png. tif, html, and txt files, for example. Multiple filebundles, such as .zip files, for which a view or launch file can bedesignated, are also supported. Furthermore, multiple versions of thesame document can also be supported.

Document version views are provided for units, equipment, and protectedsystems to display document version details and a list of files within adocument version.

Document uploaders are provided for units, equipment, and protectedsystems for use to access local standard browsers and to transmitselected document files or multiple file bundles to the EvaluationSystem server.

Various additional support functions are provided as described below:

A Site Administration function is provided to access the person,repository, database, and backups browsers access the siteconfiguration, site availability, install updates, databaseadministration, import plant, and freeze plant utilities access the siteload graph set token expiry options view log file statistics and accesslog files launch any Evaluation System page

A Site Configuration function is provided for setting access levels foradd plant, mail users, and tasks queue; and setting units system for newplants access the parameters browser.

A Configuration Browser function is provided for viewing, editing,adding and deleting site configuration parameters. A Configuration Viewfunction is used for editing and adding site configuration parameters.

A Person Browser function is provided for viewing person lists;accessing person details; adding and deleting persons and email users. aPerson View function is provided for viewing, entering, or editingperson details; and setting access levels and batch email inclusion fora person. A Logins Browser function is provided for viewing and sortingthe logins log.

A Trouble Log Analysis Browser is provided for viewing and sorting thetrouble log analysis table; and accessing trouble log analysis detailsAccessing the Trouble Log Analysis Browser To access the trouble loganalysis browser In the trouble log browser, pick the Analyze Troublelink.

A Site Availability Utility is provided for entering and activating adown time message; and adding, editing, or deleting site down times.

A Database Administration Utilities function is used for editingdatabase configuration parameters; converting database versions;re-indexing database tables; clearing persistent locks; reaping old orunreferenced worksheet specifications; and accessing the currentdatabase version.

A Reap Worksheet Specifications function is used for deleting unusedworksheet specifications. A Reap Worksheet Files function is alsoprovided. A Database Browser function is provided for locating databaseobjects by class or location. A Backups Manager and a Page TimingStatistics function is also provided.

A Site Administration Reports function is provided for accessing thesite administration reports.

A Repository Area Browser function is provided for viewing therepository area list access repository area details, and adding anddeleting repository areas.

A Repository Area View function is provided for viewing, entering orediting repository area details; sorting and sequencing the area packagelist; and adding, viewing, launching or deleting area packages.

An Area Packages Sequencer function is provided for changing the orderin which area packages are considered and displayed.

A Repository Package View function is provided for viewing, entering orediting area package details; downloading a package for editing;designating or viewing a launch file for a package; and adding, viewingor deleting package versions.

Pick the Add Package link to add a package and access a blank repositorypackage view in which to enter new package details.

A Repository Version View function is used for viewing, entering orediting details for a version of a repository area package; uploading ordownloading a package version; designating or viewing launch files for apackage; and opening individual files within a package version.

A Repository Package Uploader function for locating and selecting filesto upload as versions of repository area packages.

The Evaluation System in its preferred embodiments can be installed inboth MS Windows and Unix/Linux environments.

The Evaluation System report generation subsystem will be able togenerate a number of reports, including:

A. Library Reports including:

-   -   Plants List Report;    -   Default Std. OVPs;    -   Devices in Database;    -   Hazards in Database;    -   Pipe Fittings List;    -   ANSI Pipe Schedule; and    -   Std. Fitting Heights.

B. Plant Reports including:

-   -   Plant Data Sheet;    -   Plant Units System;    -   Plant Std. OVPs;    -   Plant/Unit Recheck; and    -   Impact Analysis.

C. Unit Reports including:

-   -   Unit Data Sheet;    -   Unit Drawings;    -   Unit Drawing;    -   Unit Equipment List;    -   Relief Device Summary;    -   Unit Systems List;    -   Unit Systems Stat's; and    -   Unit Documents.

D. Equipment Reports including:

Equipment Data Sheet;

-   -   Equip't ASME Data Sheet;    -   Equip't ISA CV Data Sheet;    -   Equip't ISA PRV Data Sheet;    -   Equip't ISA RD Data Sheet;    -   Equipment ISO Drawing;    -   Equipment P&ID Drawing;    -   Relief Device Design Record;    -   Relief Device Worksheet;    -   Contingency Analysis;    -   Contingency Summary;    -   Contingency Calculations;    -   Contingency Calc. Summary;    -   Equip't Design & Selection;    -   Piping and Fittings;    -   Piping Losses;    -   Findings & Deficiencies;    -   Equipment Documents;    -   Equipment Document;    -   Document Version;    -   Equip't Maintenance List; and    -   Equip't Maintenance Item.

E. Protected System Reports including:

-   -   System Summary;    -   System Flow Sketch;    -   Contingency Analysis;    -   Contingency Summary;    -   Contingency Calc's;    -   System Piping Losses;    -   System Revisions; and    -   System Documents.

F. Contingency Reports including:

-   -   Scenario Calculations; and    -   Scenario Piping Losses.

G. Worksheet Reports

H. Repository Reports including:

-   -   Repository Areas;    -   Repository Area;    -   Repository Package; and    -   Repository Version.

I. Tasks Queue Reports

J. Person Reports including:

-   -   Users List;    -   Admin. Details; and    -   User's Details.

K. Administration Reports including:

-   -   Site Configuration Report;    -   Site Transactions Report;    -   Database Statistics Report; and    -   Document Statistics Report.

The invention has been described hereinabove using specific examples andembodiments; however, it will be understood by those skilled in the artthat various alternatives may be used and equivalents may be substitutedfor elements and/or steps described herein, without deviating from thescope of the invention. Modifications may be necessary to adapt theinvention to a particular situation or to particular needs withoutdeparting from the scope of the invention. It is intended that theinvention not be limited to the particular implementations andembodiments described herein, but that the claims be given theirbroadest interpretation to cover all embodiments, literal or equivalent,disclosed or not, covered thereby.

Finally, the Evaluation System is designed to support the followingIndustry standards represented by the following documents, allincorporated by reference in their entirety:

API (American Petroleum Institute) Standards

ANSI B16.34

ANSI B16.5—Pipe Flanges & Fittings

API Std 520—Part 1—Design Installation of Pressure Relieving Systems

API Std 520—Part 2—Sizing, Selection & Installation of Pressure ReliefDevices

API Std 521—Guide For Pressure Relieving & Depressuring Systems

API Std 526—Flanged Steel Pressure Relief Valves

API Std 527—Seat Tightness of Pressure Relief Valves

API 576—Inspection of Pressure Relief Devices

API-2000—Venting Atmosphere and Low-pressure Storage Tanks

American Society of Mechanical Engineers Regulations

ASME Section I—Power Boilers

ASME Section III—Rules for Construction of Nuclear Facility Components

ASME Section VIII—Div 1—Pressure Vessels

ASME NB-18—National Board Pressure Relief Device Certifications

Occupational Safety and Health Administration

1910.119—Process Safety Management of Highly Hazardous Chemicals

Crane Technical Paper

Flow of Fluids Through Valves, Fittings, and Pipe

1-19. (canceled)
 20. An evaluation system for evaluating a coolingsystem of a nuclear power plant, said cooling system using water as thecoolant and comprising a plurality of nuclear plant equipment includinga protection device for protecting the cooling system, said evaluationsystem comprising: a storage subsystem for storing an equipment databaseincluding equipment information representing each of said plurality ofnuclear plant equipment, said storage subsystem also for updating saidequipment information with updated equipment information; a server forserving content, via a public communication network, to an applicationexecuting on a user computer, said server further for serving additionalcontent, including at least a portion of said content, via thecommunication network, to the application or another applicationexecuting on another user computer; a reception subsystem for receivingsaid updated equipment information for providing to said storagesubsystem, said receiving from one or both of the user computer and theanother user computer via the communication network; an assessmentsubsystem for automatically determining, by utilizing said equipmentinformation, an adequacy of the protection device for protecting thecooling system, and for generating protection assessment informationtherefrom, said protection assessment information also being stored insaid equipment database, or in another database, by said storagesubsystem; and a report generation subsystem for generating a nuclearsafety assessment report utilizing some portion of said protectionassessment information and some portion of said equipment information,wherein said content includes some portion of said equipment informationand further includes some portion of said protection assessmentinformation, and wherein said assessment subsystem is further forupdating said protection assessment information by utilizing saidupdated equipment information, and further wherein said server isfurther for serving updated content including some portion of saidupdated protection information to the user computer and/or the anotheruser computer via the communication network, wherein said nuclear safetyassessment report is of a format supporting a licensing or certificationprocess for the nuclear power plant.
 21. A method for evaluating anuclear plant using a computerized system comprising a database and aprocessor executing software for evaluating a plurality of equipment ofa pressure system for the nuclear plant, said method comprising thesteps of: storing equipment description information in the database,said equipment information describing said plurality of pressureequipment and also describing said one or more safety devices; storingphysical properties data in the database, said physical properties datapertaining to equipment of said pressure system including one or moresafety devices; automatically evaluating a performance of the pressuresystem by using the physical properties data pertaining to the equipmentinformation; and automatically generating an evaluation reportdescribing said performance.
 22. The method of claim 21, wherein saidmethod further includes the step of evaluating one or more changes thathave been made or that are proposed to be made to the pressure system,and wherein said evaluation report includes an assessment of one or moreimpacts of said changes to said pressure system.
 23. The method of claim22, wherein information in said evaluation report evaluates the safetymargins of the pressure system.
 24. The method of claim 22, wherein adescription of said changes includes an assessment as to whether any ofsaid one or more changes impact the licensing or certificationrequirements of said nuclear plant.
 25. The method of claim 21, whereininformation in said evaluation report provides information evaluatingthe design, certification, or rules changes on the pressure system. 26.The method of claim 21, wherein said method further includes the step ofevaluating one or more proposed designs or changes that have been madeor that are proposed to be made to the pressure system, and wherein saidevaluation report provides a determination of whether the proposeddesigns or changes meet required licensing or certificationrequirements.
 27. The method of claim 21, wherein said evaluation reportincludes information for supporting a certification or licensing of atleast part of said nuclear plant.
 28. The method of claim 21, whereinsaid method further includes the step of evaluating one or more proposedrequirements changes that have been made or that are proposed to be madefor nuclear plant licensing or certification, and wherein saidevaluation report provides an evaluation of the pressure system withrespect to the proposed requirements changes.
 29. The method of claim21, wherein said evaluation report supports an auditing process of thenuclear plant.
 30. The method of claim 21, wherein said evaluationreport is specifically adapted to support a design, licensing, auditingor certification process of the nuclear plant.
 31. The method of claim21, wherein said evaluation report supports a design process of thenuclear plant, a certification process of the nuclear plant, andrecurring licensing of the nuclear plant.
 32. A method for evaluating anuclear plant for regulatory compliance using a computerized systemcomprising a database and a processor executing software for evaluatinga plurality of equipment of a pressure system for the nuclear plant,said method comprising the steps of: storing equipment descriptioninformation in the database, said equipment information describing theplurality of equipment of the pressure system; storing physicalproperties data in the database, said physical properties datapertaining to said equipment; storing safety margins relatingexclusively to the nuclear industry; automatically evaluating thepressure system using the physical properties data pertaining to theequipment information to determine compliance of said pressure systemwith respect to the stored safety margins; and automatically generatingan evaluation report based on said determined compliance.
 33. The methodof claim 32, wherein said evaluation report is adapted to supporting thedesign, licensing, auditing or certification process of the nuclearplant, wherein said report .
 34. The method of claim 32, furthercomprising the step of automatically determining whether proposeddesigns, or changes to existing designs, meet required licensingrequirements or support a design certification process.